home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20041116-20060924
/
000347_fdc@columbia.edu_Thu May 11 15:44:57 2006.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Path: newsmaster.cc.columbia.edu!not-for-mail
From: Frank da Cruz <fdc@columbia.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Script compiling / encrypting?
Date: 11 May 2006 19:44:44 GMT
Organization: Columbia University
Lines: 26
Message-ID: <slrne6751c.r56.fdc@sesame.cc.columbia.edu>
References: <1147371315.638050.245860@j73g2000cwa.googlegroups.com>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1147376684 20079 128.59.59.56 (11 May 2006 19:44:44 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 11 May 2006 19:44:44 GMT
User-Agent: slrn/0.9.8.0 (SunOS)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15604
On 2006-05-11, quertyq <quertyq@hotmail.com> wrote:
: Is there any way that I can compile, encrypt, or hide Kermit scripting
: so that the end user does not see the code?
:
There is no Kermit script compiler. Encryption, of course, is a possibility
but you would have to decrypt the script before use, which would require
entry or storage of a key in the clear, which would defeat the purpose.
In Unix, you might think you could give the script a "kerbang line" and
execute-but-not-read permission, but this doesn't work because then Kermit
itself can't read the script, just like what happens with shell scripts.
Anyway, before Kermit can execute commands, it has to receive them in clear
text. Even if the script itself were hidden from the user, it would still
be possible to SET TAKE ECHO ON, SET MACRO ECHO ON, and/or LOG DEBUG to
see the commands that are being executed.
Offhand, the only solution I can think of would be to write the script as
a macro and then build it into the Kermit binary itself (you can see some
examples of predefined macros in ckuus5.c), then set the binary execute-only.
And remove the SET MACRO ECHO ON and LOG DEBUG commands!
Maybe if you explain why you don't want the user to see the code, another
approach can be suggested.
- Frank